Create a New Story Bible
- Choose File > New Story Bible.
- Select a folder and name for the new
.StoryBiblefile. - The app creates the database structure automatically and opens the new file.
User Guide
KCG Story Bible is a desktop reference system for planning worlds, characters, story structure, lore,
production notes, and supporting files inside a single .StoryBible database. It is designed to
keep worldbuilding and drafting details organized while still making them easy to export and share.
Use the File menu to create a new story bible or reopen an existing one. The main window stays centered on the same workflow: pick a section, select a record, and use the action buttons along the bottom.
.StoryBible file..StoryBible file.There is no separate global save command. When you open an editor and press Savethat record is written directly to the open database.
.StoryBible file before major story revisions. One copied file gives you a full snapshot of the project at that point in time.
The application uses a section list on the left and a data view on the right. The right side changes based on the active section.
Use the Genre/Tone button to store book-level guidance that applies to the entire project instead of a single record.
Choose a genre from the built-in list or type your own custom genre text.
Pick a primary tone, environmental mood, and narrative pacing, then select up to three voice styles.
The story profile is saved directly into the open .StoryBible file and is included in Word, PDF, and Excel exports.
These sections hold the main story-world records. They each use a dedicated editor window that matches the data they need to store.
Stores a world or realm name, its system or galaxy, and a lore summary.
Stores a location name, linked world, geography, climate, and culture notes.
Stores a character name, role, faction, home world, physical description, and profile.
Stores events with title, date, description, and a numeric order field for sorting.
Stores story beats with title, act, point of view, and summary.
Stores rule categories, rule names, effects, and limitations.
Stores two characters, the relationship type between them, and the current status of that relationship.
Stores important items, ownership, location, and notes.
Stores references to external files, along with a description and a saved path that can be opened from the main window.
These sections use one flexible editor layout. Each record includes Title, Subcategory, Focus, Summary, and Details.
Use for character goals, faction goals, story objectives, scene purposes, and outcome tracking.
Use for central ideas, recurring questions, symbolic arguments, motifs, and interpretive framing.
Use for continuity anchors, immutable facts, recurring symbols, and details that should never drift between drafts.
Use for factions, organizations, religions, customs, rituals, folklore, and social expectations.
Use for major historical events, eras, legends, glossary entries, naming systems, and inherited world memory.
Use for power systems, technical rules, device specs, creatures, engineered species, or other system logic.
Use for chapter logs, scene planning, themes, motifs, draft notes, revision planning, and cut material.
The basic workflow is the same in every section: create a record, fill in the fields that matter, and return later to expand it.
Select a section, click Newcomplete the editor, and press Save.
Select a row and click View/EditThe editor reopens with the saved data.
Select a row and click DeleteConfirm only when you are sure, because the app does not provide undo.
Links connect one record to another, even across different sections. This is how the app captures cross-reference relationships such as membership, appearance, ownership, origin, influence, and narrative connection.
The lower list in the link manager shows every saved link for the selected source record. Select a saved link and click Delete Link to remove it.
The Other Files section is for outside assets that are not stored inside the database itself.
The File menu includes three export commands. Each export collects the loaded database into a different format.
Creates a .docx document with the story profile, all sections, and a final Entry Links section.
Creates a printable PDF version of the story bible, including the story profile and links map.
Creates a workbook with a Story Profile worksheet, one worksheet per section, and an Entry Links worksheet.
Exports include the story profile, the main story data, the structured sections, and the saved links between records.
The app is flexible, but a little discipline makes it much more useful over time.
Use the same spelling and naming style everywhere, especially for factions, places, terms, and file labels.
Get the record into the database quickly, then return later to deepen the details.
Link records when the relationship matters to the story, not just because two entries mention each other.
Copy the .StoryBible file before big rewrites, structural changes, or editing sessions.
The Help menu provides quick access to the built-in support windows.